WCM implementation is the process of installing Content Management (WCM), configuring the global infrastructure for your WCM environment, and performing the initial implementation of iMIS sites so that they can be subsequently managed and populated by day-to-day WCM users. WCM implementation comprises the following activities:
■ Installing and configuring WCM on each web server that is used for hosting iMIS sites.
■ Implementing iMIS sites, including the optional migration of legacy content (such as e-Content Manager 5.x sites) into the WCM environment.
Note: WCM implementation involves technical decisions and possibly ASP.NET coding that staff or consultants who are familiar with server administration and ASP.NET development techniques should perform.
Who depends on this?
Your WCM implementation tasks must be completed before the people who perform site management can define the appearance and navigation structure of iMIS sites, and can define the infrastructure for the web content authoring environment.
What must be done before you can start?
You cannot perform WCM implementation tasks until after you have planned the specifics of your WCM implementation with the assistance of the various people who design, manage, and author content for your organization's sites.
Putting it all together
WCM implementation comprises two general workflows:
■ Installation and configuration entails the following actions, in this order:
□ Installing WCM on web servers.
□ Defining publishing servers for each installed instance of WCM, to control publishing to the iMIS sites hosted by that instance.
□ Scheduling content authoring workflow updates on your production application server to enable iMIS to process content expiration notices and the removal of expired content.
□ Granting security access to WCM features.
□ Defining global WCM properties.
□ (optional) Viewing publishing server error logs to troubleshoot publishing issues.
■ Website implementation entails the following actions, in this order:
□ Defining iMIS sites.
□ (optional) Adjusting the site keep-alive service.
□ (optional) Integrating hand-built master pages and themes with WCM to enable your custom web design to be used when defining iMIS sites.
□ (optional) Defining custom iParts as content types to expand the selection of iParts available to the people who perform web content authoring.
□ (optional) Defining navigation areas and breadcrumb areas for use in your master pages.
□ (optional) Extending the default search behavior to match your web design guidelines.
□ (optional) Extending the default content and index renderers to modify how content records and iParts are rendered for browser display and indexed by the search engine.
Location of the tools
You can find the tools in the following places:
■ Tools (administrative and staff views)
■ Content Management (staff views)
The functionality of each tool is the same in all places.
More